Method and a system for monitoring a quantity related to an asset

ABSTRACT

A method for automatically electronically associating vessel identity information of a vessel with an unassociated telemetric device, the unassociated telemetric device comprising a processor and being configured to detect and transmit quantity or usage data and being configured with a location sensing device, wherein the unassociated telemetric device is configured to communicate with a remote server, the method comprising the steps of: the remote server receiving the vessel identity information comprising a deployment location for the unassociated telemetric device; the unassociated telemetric device operating in accordance with an automatic action rule; in response to the unassociated telemetric device operating in accordance with the automatic action rule, the processor receiving location information of the unassociated telemetric device from the location sensing device; the unassociated telemetric device transmitting the location information; the remote server receiving the location information; the remote server correlating the location information with the vessel identity information when resolving that the location information represents that the unassociated telemetric device is within a proximity to the deployment location, and the remote server automatically electronically associating the unassociated telemetric device with the vessel identity information, resulting in the unassociated telemetric device becoming an associated telemetric device, so that when the associated telemetric device generates quantity or usage information, the quantity or usage information transmitted by the associated telemetric device is applied to a data store of the remote server related to the vessel identity information.

CROSS REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No.16/720,343 filed Dec. 19, 2019, which is a continuation of U.S. patentapplication Ser. No. 16/143,820 filed Sep. 27, 2018, now U.S. Pat. No.10,552,721 issued Feb. 4, 2020, which claims priority to and the benefitof Australian Patent Application No. 2017903959 filed Sep. 29, 2017,which is incorporated herein by reference in its entirety.

TECHNICAL FIELD

The disclosure herein generally relates to monitoring a quantity relatedto an asset, and particularly but not exclusively to monitoring aquantity of fluid within a vessel.

BACKGROUND

Fuels that are gaseous at standard ambient temperature and pressure(“gas fuels”) may comprise, for example, methane, ethane, propane,butane, pentane, and mixtures of two or more of these hydrocarbons. Gasfuels may be compressed to form a fluid in the form of liquefied gasfuel. For example, butane, propane, and fuels containing mixtures ofthese hydrocarbons may be sold as liquefied petroleum gas or liquidpropane gas, either of which may be abbreviated as LPG. A liquefied gasfuel or other fluid may be stored in a vessel, examples of which includebut are not limited to pressure vessels in the form of cylinders andtanks including LPG bulk storage vessels (“LPG bullet tanks”), andliquefied natural gas storage vessels. A vessel is a type of asset.

When a vessel is installed in the field, it is useful for a truck-basedgas delivery business (or other truck-based fluid delivery business) tobe able to remotely monitor the quantity of fluid in the vessel. Vesselfluid quantity information may assist a fluid supplier to avoid fluid“run-outs” i.e. letting the fluid quantity fall so low that the customerruns out of fluid. Fluid run-outs are very annoying for customers, andmay even prompt them to switch to a different fluid supplier. Fluidquantity information also helps fluid suppliers to avoid deliveringfluid before a vessel needs refilling. Delivering fluid before fluidquantities reach the re-fill quantity may result in trucks making moredeliveries than necessary, which may waste both labour and truck fuel,and forces fluid suppliers to operate a larger truck fleet thannecessary. Fluid delivery businesses, for example LPG gas deliverybusinesses, may have tens or hundreds of thousands of customers, so thecost of unnecessary deliveries can be significant for them.

A vessel may be fitted with a telemetry-enabled telemetric devicecapable of transmitting the fluid quantity information, which may be,for example, the output of a fluid quantity gauge. An example of a fluidquantity gauge is a float gauge located inside a LPG pressure vessel.The information transmitted by a telemetry-enabled telemetric device,for example, fluid quantity information, status reports, and alerts, istypically stored in an electronic database record. It may be necessaryto link, relate, or “associate” the transmitted information with one ormore other database records, for example a database record containinginformation about the vessel or a database record containing customerbilling information. This association enables a delivery to be made ontime to the correct vessel, and also enables the correct customer to bebilled for that delivery.

In a computer database, the association can be implemented by manuallyassociating an identifier from each of the two records, which allows theother information in those records to be associated (joined) in arelational database, for example. Therefore, a telemetry-enabledtelemetric device identifier for the telemetric device may be associatedin a computer database with a vessel identifier. The identifiersgenerally comprise a sequence of symbols that are each an alphanumericsymbol, and may be in the form of a serial code. Each vessel identifierfor a collection of vessels may be unique, and each device identifierfor a collection of devices may be unique. The identifiers may beprinted on labels fixed to the telemetry-enabled telemetric device andvessels, for example. The vessel identifier for the gas vessel maycomprise information that indicates a delivery point for gas deliveries.

Conventionally, a manual process is used to associate thetelemetry-enabled telemetric device identifier with the vesselidentifier. An installer may communicate by telephone the deviceidentifier and vessel identifier to a person at the truck-based deliverycompany's office or depot.

The person manually enters the telemetry-enabled telemetric deviceidentifier and vessel identifier into a database to make theassociation. Manual association of identifiers may be delayed orforgotten by the person doing it, which may delay the commissioning orbilling related to the vessel and/or its fluid contents.

Further, there are a number of opportunities for human errors to occurwhen manually associating identifiers, including but not limited to:

-   -   The telemetry-enabled telemetric device identifier may be        misread or confused with other markings on the telemetry-enable        device identifier, e.g. model number, asset tag.    -   The telemetry-enabled telemetric monitoring device identifier        may be recorded incorrectly in the database.    -   An incorrect vessel identifier may be associated in the computer        database with the telemetry-enabled telemetric monitoring device        identifier, which may lead to incorrect customer being billed.    -   Either an invalid vessel identifier or an invalid        telemetry-enabled telemetric device identifier may be used,        which may lead to no customer being billed at all.    -   When a telemetry-enabled telemetric monitoring device identifier        is pre-associated with the vessel identifier, an installer        carrying multiple devices may install a telemetry-enabled        telemetric device on the wrong vessel.

An incorrect association of identifiers may be a serious issue forsuppliers and consumers of delivered fluids, for example LPG gas andoil. It may result in incorrect fluid quantity information for a vessel,which may cause run-outs. It may also cause the wrong consumers beingbilled for gas/oil usage.

Mistakes may inconvenience consumers, which may cause them to switch toanother supplier, which is a loss of revenue for the supplier. Further,each incorrect device-to-vessel or other type of asset association needsto be investigated and rectified by the supplier (which may require avisit to the telemetric device in the field) which wastes time andmoney. Even a small number of incorrect device-to-vessel associationsmay be costly for a supplier. An error rate of only 1% in a roll-out of50,000 telemetric monitoring devices will result in 500 incorrectdevice-to-vessel associations, which is a major source of expense to asupplier.

SUMMARY

It is an object of the disclosed methods and devices to at leastpartially ameliorate problems described above, and others wherepossible.

Disclosed are systems and methods for automatically changing anunassociated telemetric device into an associated telemetric device.There are at least two situations an unassociated telemetric device canbecome an associated telemetric device.

In a first situation, a device may be installed for use on a vessel in adepot where, for example, a distributor may house and/or maintain astock of vessels. In that case, a commercial operator may store a vesseland then deliver it to a customer at the vessel's deployment location.Prior to delivery at the deployment location, a device may be installedon a vessel. The vessel may therefore be transported with the devicealready installed.

During transport the device may either be in a state of sleep wherein astate of switched off the power to the radio module and/or any otherfunctions of the device reduces the power consumption of the telemetricfitting electronics, which may generally extend the life of the at leastone battery. However, during transport, the device may not be asleep dueto any number of circumstances. For example, after installation at thedepot, the device may have been awakened but not returned to its sleepstate. Therefore, during transport, the device may be awake and pollingthe GNSS chip for its location, and processor may cause the radiotransmitter to transmit the location of the device during transit.However, a remote server determining the location information from adevice which is not in its deployment location, but for example close toanother deployment location, the device could be paired to the wrongdeployment location, and thus become an associated telemetric device,but associated incorrectly. It is desirable to avoid correlating atelemetric device to the wrong deployment location.

In another situation, a vessel may already be located at a deploymentlocation but may not have already, a device installed on the vessel. Orin another situation at the deployment location, there is a device on orincorporated into the vessel but for some reason the device needsreplacing. It is understood that a device on a vessel may include anytype of installation, for example, where a device is within a vessel, orotherwise incorporated with the vessel.

Disclosed herein is a method and a system for automaticallyelectronically associating a vessel's or asset's identity informationand with an unassociated telemetric device, the unassociated telemetricdevice comprising a processor and being configured to detect andtransmit of quantity or usage and being configured with a locationsensing device, wherein the unassociated telemetric device is configuredto communicate with a remote server, the method comprising the steps of:the remote server receiving the vessel identity information comprising adeployment location for the unassociated telemetric device; theunassociated telemetric device operating in accordance with an automaticaction rule; in response to the unassociated telemetric device operatingin accordance with the automatic action rule, the processor receivingthe unassociated telemetric device location information from thelocation sensing device; the unassociated telemetric device transmittingthe unassociated telemetric device location information; the remoteserver receiving the unassociated telemetric device locationinformation; the remote server correlating the unassociated telemetricdevice location information with the vessel identity information whenresolving that the unassociated telemetric device location informationrepresents that the unassociated telemetric device is within a proximityto the deployment location, and the remote server automaticallyelectronically associating the unassociated telemetric device with thevessel identity information, resulting in the unassociated telemetricdevice becoming an associated telemetric device, so that when theassociated telemetric device generates quantity or usage information,the quantity or usage information transmitted by the associatedtelemetric device is applied to a data store of the remote serverrelated to the vessel identity information.

Also disclosed herein is a method for monitoring a quantity of fluidwithin a vessel. The method comprises the steps of:

receiving telemetric device location information indicative of thelocation of a telemetric device, the telemetric device being fortransmission of fluid quantity information indicative of the quantity offluid within the vessel;

determining, using the telemetric device location information and storedtarget location information indicative of a target location, whether thetelemetric device is located at the target location, and if sodetermined, electronically associating information related to thetelemetric device with information related to the vessel.

An embodiment comprises the step of determining whether the telemetricdevice is not located at the location of the vessel using the vessellocation information and the telemetric device location information, andif so determined stop electronically associating fluid quantityinformation generated by the telemetric device with the vessel.

An embodiment comprises the step of determining, using the telemetricdevice location information and the target location information, whetherthe telemetric device is not located at the target location, and if sodetermined, stop electronically associating information related to thetelemetric device with information related to the vessel.

In an embodiment, the target location information defines a geographicalboundary, and the step of determining whether the telemetric device islocated at the target location comprises determining whether thetelemetric device is within the geographical boundary.

In an embodiment, the geographical boundary surrounds only one vesselfor which the quantity of fluid within the vessel is being monitoredwith the telemetric device.

In an embodiment, the step of determining whether the telemetric deviceis located at the target location comprises the step of determiningwhether the geographical boundary overlaps with a plurality of othergeographical boundaries for a plurality of other vessels being monitoredfor fluid quantity therein by a plurality of other telemetric devices.

In an embodiment, the target location information defines a firstgeographical boundary and the telemetric device location informationdefines a second geographical boundary, and the step of determiningwhether the telemetric device is located at the target locationcomprises determining whether the second geographic boundary overlapsthe first geographical boundary according to a predefined rule.

In an embodiment, the information related to the telemetric devicecomprises a geographical location computer database record comprising alocation of the vessel.

In an embodiment, the information related to the telemetric devicecomprises a telemetric device identity computer database recordcomprising telemetric device identity information.

In an embodiment, the information related to the vessel comprises avessel identity computer database record comprising vessel identityinformation.

In an embodiment, the information related to the telemetric devicecomprises a telemetric device identity computer database recordcomprising telemetric device identity information, and comprising thestep of determining, using the target location information and thetelemetric device location information, whether the telemetric device isnot located at the target location, and if so determined, disassociatingthe telemetric device identity record from the vessel identity record.

In an embodiment, the information related to the telemetric device isassociated with information related to the vessel when the location ofthe telemetric device is determined using telemetric device locationinformation generated by at least one of the telemetric device andanother telemetric device, the telemetric device location informationbeing indicative of the location of one of the telemetric device and theother telemetric device.

An embodiment comprises the step of operating the telemetric device inaccordance with a rule.

In an embodiment, the transmission comprises wireless transmission atradio frequencies.

Disclosed herein is a method for monitoring a quantity related to anasset. The method comprises the steps of:

receiving telemetric device location information indicative of thelocation of a telemetric device for transmission of quantity informationindicative of the quantity;

determining whether the telemetric device is located at a targetlocation using target location information and the telemetric devicelocation information, and if so determined, electronically associatinginformation related to the telemetric device with information related tothe asset.

In an embodiment, the quantity comprises at least one of a quantity of acommodity, a quantity of gas, a quantity of electrical power, a quantityof a water, and a quantity of oil.

In an embodiment, the quantity comprises at least one of a physicalquantity, a vibration quantity in a structure, and a strain quantity ina structure.

In an embodiment, the asset comprises at least one of a gas vessel, anoil vessel, a water vessel, a power pole, a manifolded gas pack, aportable building, a portable plant, and a portable piece of equipment.

In an embodiment, the target location is a deployment location for theasset.

Disclosed herein is a system for monitoring a quantity of fluid within avessel. The system comprises:

a telemetric device configured to transmit telemetric device locationinformation indicative of the location of the telemetric device andtransmit fluid quantity information indicative of the quantity of fluidwithin the vessel;

a processor configured to receive the telemetric device locationinformation, determine whether the telemetric device is located at atarget location using the telemetric device location information andtarget location information indicative of the target location, and if sodetermined, electronically associate information related to thetelemetric device with information related to the vessel.

In an embodiment, the telemetric device is configured to wirelesslytransmit at radio frequencies the telemetric device location informationand the fluid quantity information.

In an embodiment, the processor comprises an electronic data store inwhich the information related to the telemetric device is electronicallyassociated with the vessel.

In an embodiment, the telemetric device is configured to generate thetelemetric device location information.

An embodiment is configured to locate the telemetric device using radiotriangulation.

In an embodiment, the telemetric device comprises a fluid quantitysensor.

Disclosed herein is a system for monitoring a quantity related to anasset. The system comprises:

a telemetric device configured to transmit telemetric device locationinformation indicative of the location of the telemetric device andtransmit quantity information indicative of the quantity;

a processor configured to receive the telemetric device locationinformation, determine whether the telemetric device is located at atarget location using the telemetric device location information andtarget location information indicative of the target location, and if sodetermined, electronically associate information related to thetelemetric device with information related to the asset.

Disclosed herein is a processor for monitoring a quantity related to anasset. The processor is configured to receive telemetric device locationinformation from a telemetric device configured to transmit telemetricdevice location information indicative of the location of the telemetricdevice and transmit quantity information indicative of the quantity,determine whether the telemetric device is located at a target locationusing the telemetric device location information and target locationinformation indicative of the target location, and if so determined,electronically associate information related to the telemetric devicewith information related to the asset.

An embodiment is configured to transmit telemetric device locationinformation indicative of the location of the telemetric device andtransmit quantity information indicative of the quantity.

Disclosed herein is a method for electronically associating, in acomputer database, a first database record with a second databaserecord. The second database record comprises information related to atelemetric device. The method comprises the steps of:

receiving telemetric device location information indicative of alocation of the telemetric device;

determining whether the telemetric device is located at a targetlocation, and if so determined, electronically associating the firstdatabase record with the second database record.

An embodiment comprises the step of determining whether the telemetricdevice is not located at the target location, and if so determined,disassociating the first database record from the second databaserecord.

In an embodiment, the step of determining whether the telemetric deviceis located at the target location comprises comparing the telemetricdevice location information with stored target location informationindicative of the target location.

In an embodiment, the step of determining whether the telemetric deviceis located at the target location comprises:

comparing the telemetric device location information with stored targetlocation information indicative of the target location, the targetlocation information defining a target geographical boundary determiningwhether the telemetric device is within the target geographicalboundary.

In an embodiment, the step of determining whether the telemetric deviceis located at the target location comprises:

comparing the telemetric device location information with stored targetlocation information indicative of the target location, the targetlocation information defining a first geographical boundary, thetelemetric device information defining a second geographical boundarydetermining whether the second geographic boundary overlaps the firstgeographical boundary according to a predefined rule.

In an embodiment, the step of comparing the telemetric device locationinformation with stored target location information is performedelectronically.

In an embodiment, the telemetric device location information is receivedthrough wireless transmission at radio frequencies.

In an embodiment, the first database record comprises informationrelated to an asset.

In an embodiment, the first database record comprises informationrelated to a deployment location of an asset.

In an embodiment, the telemetric device is arranged to monitor aquantity related to an asset and to transmit quantity informationindicative of the quantity.

In an embodiment, the asset comprises a vessel for holding a fluid.

Any of the various features of each of the above disclosures, and of thevarious features of the embodiments described below, can be combined assuitable and desired.

Any of the various features of each of the above disclosures, and of thevarious features of the embodiments described below, can be combined assuitable and desired.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments will now be described by way of example only with referenceto the accompanying figures in which:

FIG. 1 shows a block diagram of an embodiment of a system for monitoringa quantity related to an asset.

FIGS. 2 to 12 show an embodiment of a telemetric device for monitoring aquantity related to an asset.

FIGS. 13 to 16 show plan views of a telemetric device and asset beforeand after moving toward and to a deployment location and therefore afterassociation.

FIGS. 17 to 18 show an example of tables of information in an SQLdatabase.

FIGS. 19 to 21 shows various alternative architectures for embodimentsof systems for monitoring a quantity related to an asset.

DETAILED DESCRIPTION OF THE EMBODIMENTS

FIG. 1 shows a block diagram of an embodiment of a system for monitoringa quantity related to an asset. The system is generally indicated by thenumeral 10. The system 10 comprises a telemetric device 12 configured totransmit telemetric device location information 14 indicative of thelocation of the telemetric device and to transmit quantity information16 indicative of the quantity. The system 10 comprises a firstunassociated telemetric device 12 and a remote server or other devicesuch as a mobile device 18. The unassociated telemetric device isconfigured with a location sensing device such as a GNSS device, and acontents and/or usage sensing device for sensing the contents or usageof contents of an asset. The asset, for example, may be a vessel. Thevessel, tank or asset described herein is a vessel in the form of a LPGbulk storage tank of FIG. 1, but the vessel may alternatively be any ofa cylinder or a tank for any suitable fluid, solids, gas or any type ofproduct, examples of which include liquefied gas fuel, liquefiedammonia, cryogenic liquids including liquefied natural gas and liquefiedpermanent gases, water, solutions, liquid chemicals, and refinedpetroleum products including petrol, kerosene, and fuel oil.Furthermore, the tank can be more generally referred to as an asset,wherein the asset can be, for example, any fuel handling, storagesystems or any commodities distribution enclosure. While a magneticallyenabled float gauge fuel-level sensor system is typically used in an LPGor oil tank, it is understood that a product-level sensing device can beenabled by any type of technology, for example, ultra-sound/ultrasonic,optical, pressure, ammeters, voltmeters, weight, laser, microwave andany other type of sensor system and any product-level detection iswithin the scope of this discussion. In another embodiment, thetelemetric electronic device 12 may be incorporated into the asset as apart of the asset, in any suitable manner.

The remote server includes at least one processor 18 configured toreceive the unassociated telemetric device location information 14 basedupon GNSS device data of the unassociated telemetric device 12 and canreceive the quantity information 16 based upon sensor device data of theassociated telemetric device 12 when so transmitted. Other remoteddevice configurations are within the scope of this discussion.

In one scenario, the vessel is delivered within the target location 21with a pre-installed unassociated device 12. In another scenario, thevessel is already at the deployment location 22 within the targetlocation 21 and the unassociated device 12 is thereafter installed foruse in conjunction with the vessel. Therefore, the vessel may be atdeployed at a location 22 within a target location 21, with or withoutthe device 12. The target location may be described as geographicalboundary of any suitable dimensions.

In any event, the system 10 can determine whether the unassociatedtelemetric device 12 is located at a target location 21 (in the vicinityof where an asset 22 is deployed) using the unassociated telemetricdevice location information 14. Because a location device of theunassociated device 12 may be a GNSS, activation of the GNSS may beperformed on a limited basis, as such GNSS devices draw substantialpower from the device's battery. The housing of the device may be sealedto maintain its integrity in adverse weather conditions, so therefore,when the batteries are depleted, the device may be need to be replaced.Therefore, drain on the battery may be avoided by transmitting locationinformation 16 on a limited basis. The trigger for the unassociatedtelemetric device 12 to activate the location device may be when thedevice operates in accordance with an automatic action rule.

When the unassociated telemetric device location information 14 is sotransmitted, it can be determined or resolved whether the telemetricdevice 12 is located at a target location 21 (in the vicinity orproximity to where an asset 22 is deployed). Using the unassociatedtelemetric device location information 14 and target locationinformation 20 indicative of the deployment location of the asset, andif it is so determined or resolved that the device's 12 is within the tothe target location 21 or otherwise proximal to the asset's deploymentlocation, fully or partially (within tolerances such the boundarydimension for the telemetric device as described), then the system canelectronically associate the unassociated telemetric device with theasset identity information. In this way, quantity or usage informationtransmission output of the associated telemetric device can be appliedto a data store of the remote service related to the asset identityinformation as the now the output of the associated telemetric device 12is correlated with information related to the asset 22.

The device deployment location may be received at a remote locationand/or server, may be combined with a perimeter boundary which enlargesthe area around the device's deployment location. The accuracy of thelocation information provided by various commercially available chipsetstypically has a tolerance associated with it and may be used to defineperimeter boundary. Other parameters may be used to define the perimeterboundary, alternatively or as well. The perimeter boundary superimposedupon the deployment location information received from the device 30,for example, may exceed the tolerance. For example, the perimeterboundary superimposed upon the location information may have a radius of10 meters, and therefore a boundary dimension may be applied to thedevice location information to enlarge the device location information.The enlarged device location information may overlap the target locationinformation (which may be superimposed over the deployment location)when the remote server compares the determined location information withthe target location information.

The system 10 is configured to perform a method for monitoring aquantity related to an asset. A step of the method comprises receivingtelemetric device location information 14 indicative of the location ofa telemetric device for transmission of quantity information 16indicative of the quantity. A step of the method comprises determiningwhether the telemetric device 12 is located at a target location 21(where an asset 22 is deployed) using target location information andthe telemetric device location information 14, and if so determined,electronically associating information related to the telemetric device12 with information related to the asset 22. The processor may comprisea computer program, which when executed by the processor causes theprocessor to perform the embodiment disclosed above.

This but not all embodiments of the system 10 is for monitoring a levelof fluid within a vessel, however it will be appreciated the otherembodiments may be for monitoring generally any suitable quantityrelated to any suitable asset. In this embodiment, the asset is a vesseland the quantity is the level of fluid within the vessel. However, otherexamples of an asset include:

-   -   a gas vessel, oil vessel, or water vessel;    -   a power pole;    -   a gas meter or electrical meter;    -   a manifolded gas pack;    -   a portable building;    -   portable plant or equipment.

In at least some embodiments, the asset is stationary in use but capableof being transported to an installation site.

FIG. 2 shows a perspective view of an embodiment of a telemetric devicein the form of a telemetric fitting 30 for an asset in the form of avessel 35 for holding liquefied gas. The telemetric fitting 30 isconfigured to derive liquid-level information when fitted to aliquid-level gauge 37 on the vessel 35, and to wirelessly transmit atradio frequencies the liquid-level information.

In the example shown in FIG. 2, the vessel is a pressure vessel in theform of a liquefied gas fuel pressure storage vessel, specifically anLPG bulk storage pressure vessel, however the vessel may be any suitablepressurized or non-pressurized vessel, examples of which include a LPGcylinder, a cryogenic vessel for a permanent gas, liquefied natural gasor other fluid, an ammonia storage vessel, and a refined petroleumproduct storage vessel for example. The liquid level gauge 37 encloses adrive magnet connected to a float-arm gauge inside the vessel, and thedrive magnet rotates in response to changes in liquid level inside thevessel. However, generally any suitable liquid-level gauge may be used.

FIG. 3 shows a block diagram of telemetric fitting electronics 58.Connecting lines with arrows are information conduits, and connectinglines without arrows are power conduits. The electronics comprises atleast one printed circuit board assembly (PCBA) 57, 59. The electronics58 comprises a plurality of electrical components, at least some ofwhich are mounted on a printed circuit board of the at least one PCBA57, 59. The plurality of electrical components comprise at least one ofa processor 60 in the form of a logic device, in this embodiment a hostmicrocontroller unit 60, an electronic magnetic sensor 64 in the form ofan electronic magnetic field angle sensor (which is analogue, however itmay alternatively be digital), a location sensing device such as a GNSSchip 73, and a radio 71 in the form of a radio transceiver, the radiocomprising at least one of a medium range radio network interface and along range radio network interface, an antenna 72, and a power switch inthe form of a MOSFET 68, indicator lights in the form of at least oneLED 66, and an electrical power source in the form of at least onebattery 62 that provides power to the radio 71 via the MOSFET 68 and thelogic device 60. The processor 60 is in electrical communication withthe MOSFET 68. The MOSFET 68 and the processor 60 cooperate to switchoff the power to the radio 71 when it is not transmitting theliquid-level information.

Another form of switch, for example a relay, may be used instead. Theradio 71 is within a module, which may consume more power than desired,even when not transmitting. Switching off the power to the radio moduleand/or any other functions of the device reduces the power consumptionof the telemetric fitting electronics 58, which may generally extendsthe life of the at least one battery 62 to, for example, 15 years. In analternative embodiment, the electrical power source comprises an energyharvesting system that harvest mechanical energy (e.g. vibrations),electromagnetic energy (e.g. radio waves, light), or heat. For example,the energy harvesting system may comprise a solar cell, orpiezo-electric generator.

Medium-to-long range wireless links enables transmission to centralizeddata centers, for example, using either private or commercial radio basestations.

In this embodiment, the radio network interface comprises a low powerwide area network (LPWAN) interface. The LPWAN interface comprises anLPWAN integrated circuit 70. The LPWAN interface comprises a physicalLPWAN interface in communication with the antenna 72. LPWAN is a type ofwireless communications network for medium to long range communicationsat generally, but not necessarily, low bit rates and has low powerconsumption when compared to cellular communication technologies forvoice and high bandwidth data services. Examples of LPWAN include butare not limited to LoRa, and SIGFOX. The LPWAN radio integrated circuitmay be within a LPWAN radio module. Alternative embodiments may have aradio 71 comprising another type of medium range radio network interfaceor long range radio network interface, for example a cellular radionetwork interface (examples of which include but are not limited to GSM,CDMA, and LTE cellular radio network interfaces), IEEE 802.11 interface(“Wi-Fi”) and a satellite communications interface.

The electronic magnetic field angle sensor 64 may not be sensitive toambient temperature changes, as magnetic field strength sensorsgenerally are. Consequently, the use of an electronic magnetic fieldangle sensor 64 may increase accuracy. In alternative embodiments,however, the strength of the magnetic field may be sensed for derivingthe liquid-level measurement.

FIGS. 4-6 show perspective views of the PCBAs 57 and 59 which areorthogonal to each other and are joined using a board-to-board connectorin the form of a header.

FIGS. 7 and 8 show an exploded perspective view and a cutaway view ofthe telemetric fitting 30 respectively. The telemetric fitting 30 has agauge interface 32 at an end 36 of opposite ends 36, 102 thereof. Thegauge interface 32 is configured to derive liquid-level information fromthe liquid-level gauge 37, for example in this embodiment from theliquid-level dependent magnetic field generated by the liquid-levelgauge. The telemetric fitting 30 is configured such that the magneticfield generated by the drive magnet in the liquid-level gauge rotatesaround a longitudinal axis thereof. The magnetic field generated by theliquid-level gauge may be sensed directly by the electronic magneticsensor 64. In this embodiment, however, at least one ferromagneticelement 42, 43 (two in the present embodiment, however other embodimentsmay have more or less) follows the magnetic field of the drive magnet,and the magnetic field of the ferromagnetic element 42 is sensed by theelectronic magnetic sensor 64.

FIG. 11 shows a cross-sectional view of the liquid-level sensor head 19,drive magnet 47 and ferromagnetic element 42, 43. The ferromagneticelement 42, 43 and the electronic magnetic sensor 64 are parts of amagnetic sensor shown approximately in FIG. 11, with a more accuratedetail thereof shown in FIG. 12 without magnets. In use, the magneticsensor 64 is magnetically coupled to the magnetic field generated bydrive magnet 47 within the liquid-level sensor head 19. The at least oneferromagnetic element 42, 43 is intermediate the end 36 and the sensor64 and the PCBA 57. The magnetic sensor senses the orientation of themagnetic field generated by the liquid level gauge, which is dependenton the liquid-level within the vessel.

The magnet 42 is in this embodiment is one of two magnets 42, 43arranged symmetrically around a central axis and held by a ferromagneticelement holder 49 in the form of a magnet holder. The magnet holder 49is supported by a journal 41 to form a rotary bearing assembly 45 forrotation of the magnetic holder 49 around the longitudinal axis,enabling the at least one ferromagnetic element 42, 43 to rotate withthe liquid-level dependent magnetic field. A bearing surface 51 withinthe magnetic holder receives the journal 41. The journal 41 is in theform of a peg or spigot, which in this but not all embodiments isintegral with the end 36. The journal 41 penetrates more than half waythrough the magnetic holder 49, which may provide superior balance. Thebearing assembly 45 comprises a first bearing component 53 in the formof a thrust bearing at the tip of the journal 41 for supporting themagnet holder 49, and a second bearing component in the form of a radialbearing 55 for orientating the magnet holder 49 to the central axis,especially when one magnet is misaligned or has a magnetic strength thatis not equal to the other magnet. The magnet holder 49 is held down onthe journal 41 by the magnetic attraction of the at least one magnet 42,43 to the drive magnet 47 within the liquid-level sensor head 19, whichgenerally but not necessarily removes the need for a second journalengaged with the other side of the magnetic holder.

The journal and the bearing surface comprise dissimilar materials for alow coefficient of friction. The materials are selected for a lowcoefficient of friction to maximize the bearing performance. In thisembodiment, the journal is polycarbonate and the magnet holder isPolyOxyMethylene (“ACETAL”), however any suitable materials may be used.

The magnets 42, 43 have opposite magnetic orientation. Since like polesrepel and opposite poles attract, this ensures that the correct magnets42, 43 are correctly matched to the arms of the arms of the shaped drivemagnet 47 in the liquid-level sensor head 19, which generates theliquid-level dependent magnetic field. Without the opposite magneticorientations, it is possible for the magnets to be 180 degrees in error,which may result in a spurious reading.

The microcontroller unit 60 (indicated in FIGS. 3 and 4) receives rawmagnetic field information in the form of magnetic field orientationinformation generated by the magnetic sensor, in this embodiment from anoutput of the electronic magnetic sensor 64 shown in FIG. 11. Themagnetic field orientation information comprises three voltages fromthree arms of a bridge within the sensor 64. The microcontrollerexecutes a program that comprises an algorithm specified by the sensormanufacturer for calculating magnetic field orientation informationindicative of an angle of the magnetic field from the received rawmagnetic field information. The magnetic field orientation informationis indicative of the liquid-level. The magnetic field orientationinformation comprises a string of symbols that encode an angle for theorientation of the magnetic field. The microcontroller 60 sends themagnetic field orientation information to the radio for transmission ofthe liquid level information. The radio encapsulates the string ofsymbols in accordance with the LPWAN protocol and subsequently sends theencapsulated string of symbols, optionally together with telemetricfixture identification information indicative of the identification ofthe telemetric fixture. The LPWAN protocol may include identificationinformation, for example a SigFox DeviceID or LoRaWAN end-deviceaddress. The magnetic field orientation information is received by acomputer server that can access information on the type of gauge thatthe telemetric unit 30 is attached to and thus calculate using themagnetic field orientation information the liquid-level in a percentageof total vessel water volume or generally any suitable other unit, forexample volume of remaining liquid in the vessel. The computer serverhas a data store in the form of a database that associates theidentification information of a plurality of telemetric fixtures toinformation about the gauge and/or vessel to which they are eachattached. The database may be populated by keyboard entry, for example.

In an alternative embodiment, the microcontroller unit 60 has a lookuptable stored in memory associating the sensed magnetic field angle withliquid-level information. Generally, any suitable algorithm may be usedto derive the liquid-level information from the magnetic fieldinformation generated by the magnetic sensor. In this but not allembodiments, the liquid-level information comprises a string of symbolsthat encode the remaining volume of liquid as a percentage. Themicrocontroller determines the liquid-level information from the lookuptable and subsequently sends the liquid level information to the radiofor transmission, of the liquid level information. The radioencapsulates the string of symbols in accordance with the LPWAN protocoland subsequently sends the encapsulated string of symbols, together withtelemetric fixture identification information indicative of theidentification of the telemetric fixture.

Coupled to the ferromagnetic element 42 is an indicator 44 in the formof a disk having an index mark or pointer 48. The index mark or pointermay be pad printed, a label attached with adhesive, or otherwise formedor made for example by laser machining. The indicator 44 is attached viaa clip to the magnet holder and rotates with the ferromagnetic element.The telemetric fitting 30 comprises a two-part transparent exteriorhousing 38, made of impact resistant polycarbonate, in which is disposedelectronics 58. The polycarbonate has a transparent window 39 at the end36 for viewing the indicator 44 in the form of the disk from above. Thedial 40 is also transparent.

A human readable dial 40 is attached to the exterior housing 38. Thedial is attached the housing adjacent the gauge interface 32. Theindicator 44 cooperates with the dial 44 for indicating the liquid-levelin the vessel. For example, the dial may have a scale having thepercentage of the vessel's water volume printed thereon, or may have“FULL”, “REFILL” and “EMPTY”, colour or other coding for the liquidlevel. The dial is oriented to the longitudinal axis of the telemetricfitting 30 for viewing from above.

FIG. 9 shows a top view of the telemetric fitting 30, the dial 40 andthe pointer 48. The telemetric fitting 30, and consequently the exteriorhousing 38, does not extend beyond a perimeter 42 of the gauge head 19when attached to the liquid-level gauge 10.

The physical location of the telemetric device may be used toautomatically associate information related to the telemetric devicewith information related to an asset.

When the telemetric device is determined to be at the target location,the system automatically makes an association in a computer database ofinformation related to the telemetric device with information related tothe asset. Conversely, when the telemetric device is determined to nolonger be located at the target location, the system may automaticallyremove an existing association in the computer database betweeninformation related to the telemetric device and information related tothe asset. In other words the system “disassociates” information relatedto the telemetric device and information related to the asset.

In one embodiment, the target location is a region which includes thecurrent location of the asset. This situation may arise when the assethas been installed at the target location without the telemetric device.The automatic association occurs when the telemetric device reaches thetarget area.

In another embodiment, the target location is a future deploymentlocation for an asset, such as a customer address. This situation mayarise when the telemetric device has been installed at the asset beforethe asset has been deployed in the target area. The automaticassociation may occur when the asset and telemetric device are movedtogether into the target area.

The telemetric device location, asset location and target location mayeach be defined by a geolocation space (GLS), which may be a point,two-dimensional region, or three-dimensional space. An example of apoint is a single set of latitude & longitude coordinates, andoptionally height above sea level. An example of a two-dimensionalregion is a circle, triangle or polygon centered on a defined point, ora polygon with latitude & longitude coordinates. An example of athree-dimensional space is a sphere centered on a point, or a polyhedralcentered on a point. Other examples of locations that may be defined bya GLS include but are not limited to:

-   -   the location at which vehicles should park when making        deliveries (vehicles may need to park some distance from the        asset for safety reasons or access restrictions);    -   the location of a depot where installers collect telemetric        devices before installing them on assets;    -   the location of a store or warehouse where telemetric devices        are stored before being supplied to distributors or consumers.

Each GLS may be defined in many ways and can have a wide variety ofshapes and sizes, depending on requirements. For example, the GLS candefine:

-   -   geographic coordinates (e.g. latitude and longitude) plus rules        for defining a boundary in relation to the geographic        coordinates, for example:    -   a circular boundary with a 50 m radius centred on particular        geographic coordinates—a square boundary of a particular size        centred at distance D directly the north of particular        geographic coordinates—a boundary with a complex shape defined        by a line passing through set of:        -   geographic coordinates in a particular order;        -   a postcode zone with a defined boundary;        -   a boundary of a property at a particular address;        -   a locality, suburb, town, city or region with a defined            boundary.

If the location of the telemetric device is provided by on-board GPS,the GLS for the telemetric device may be a circle centred on a latitudeand longitude. If the position of the device is provided by cellulartriangulation, the GLS may be a compass direction and length.

The GLS can change over time. For example, a GLS indicating the locationof the telemetric device will change when the telemetric device ismoved. Also, the GLS of the telemetric device can change in shape orsize, even when the telemetric device is stationary, for example ifthere is a change in the precision of the GNSS or cell towertriangulation used to locate the telemetric device. In another example,the GLS of an asset may initially be a postcode, but subsequentlyreduced in size, for example when more precise information about thelocation of an asset is received. Alternatively, the GLS of an asset canbe moved when an asset is moved. The GLS of the telemetric device andasset may be different in size and shape. For example, the GLS for thetelemetric device may be in the form of a circular area, while the GLSfor the asset may be in the form of a suburb boundary or a propertyboundary.

Information related to the telemetric device may comprise many types forinformation, including, but not limited to:

-   -   GLS for the telemetric device location;    -   quantity information transmitted by the telemetric device (e.g.        fluid quantity information indicative of the quantity of fluid        within the vessel that the device monitors);    -   operational information related to the operational status of the        telemetric device (e.g. battery status);    -   metadata (e.g. MAC address of telemetric device, time of        transmission);    -   alerts or other messages generated by the telemetric device        (e.g. “tank empty”);    -   a serial number or other identifier for the telemetric device;    -   the name of the manufacturer of the telemetric device;    -   the brand or model name of the telemetric device;    -   the year the telemetric device was first activated.

The information related to the telemetric device may be stored in one ormore computer database records for the telemetric device. For example,information related to the telemetric device may be stored in twoassociated records: a first record containing physical details and GLSof the telemetric device; and a second record containing quantityinformation received from the telemetric device, for example fluidquantity data.

Information related to the asset can include, but is not limited to:

-   -   a GLS for a delivery point (the delivery point may be different        from the deployed asset    -   location);    -   a GLS for the asset location;    -   target location;    -   a serial number or other identifier for the asset;    -   features of the asset, for example: vessel volume, vessel shape,        type of gas contents, year of manufacture;    -   an address of a customer;    -   a suburb or postcode for the asset location;    -   customer billing information.

The information related to the asset may be stored in one or moreassociated computer database records. For example, information relatedto the asset may be stored in three associated records: a first recordcontaining physical details and GLS of the asset; a second recordcontaining customer account information; and a third record containinggas usage and billing history for the asset.

The information related to the asset can be in turn linked to otherinformation, for example:

-   -   a customer account containing a range of customer information        such billing details, billing history, contact details;    -   an account for a depot used by installers of the telemetric        device, for example an inventory of telemetric devices currently        at a depot awaiting deployment in the field;    -   an account for a store or warehouse used by suppliers of the        telemetric device, for example an inventory of telemetric        devices currently in storage and available for supply to        installers.

Any database record can be manually associated with another record inthe conventional manner.

For example, if the system automatically associates a first and secondrecord, and one of those records is manually associated with a thirdrecord, then all three records become associated with each other. Thisthree-way association only lasts while the first and second recordsremain associated. If the first and second records become disassociated,then only the manual association remains.

Software processes remote from the telemetric device can receive dataindicative of the location of the device and automatically determinewhether the telemetric device is found to be located at the targetlocation. Software processes can also perform the automatic databaseassociation of information related to the telemetric device withinformation related to the asset.

EXAMPLE 1

FIG. 13 shows a plan view of a telemetric device 201 attached to anasset 202 (e.g. an LPG vessel) before the asset is taken to a deploymentlocation centred at point 203. As discussed above, the unassociatedtelemetric device 201 may have been attached or otherwise incorporatedinto the asset at a location other than at the deployment location, andmoved with the asset to the deployment location. The target locationinformation in which a deployment location is located, defines a firstgeographical boundary and the telemetric device location informationdefines a second geographical boundary. The remote server correlatingthe location of the telemetric device with the target locationinformation comprises the remote server determining or resolving whetherthe second geographic boundary overlaps the first geographical boundaryaccording to a predefined rule.

The predefined rule for example, may set out how much and/or thedimensions of the overlap is required of the first and secondgeographical boundary. It is understood that any predefined rule thatassumes a good match is within the scope of this discussion.

The deployment location accordingly may be within a target location,such that a target location is defined by a first geographical boundaryof any suitable dimensions or size. The unassociated telemetric devicelocation information defines a second geographical boundary which may beof any suitable dimensions or size. The arrow 215 may indicate thedirection in which the asset and unassociated telemetric device aremoving which in this case is in the direction of the deploymentlocation. At some point, the first geometric boundary may overlap thesecond geometric boundary, at which point may define an event associatedwith an automatic action rule, for example, an activation event, togenerate event data

The system for changing an unassociated telemetric device into anassociated telemetric device includes that the remote server 217 can beconfigured to receive target location information (a geographicalboundary) indicative of a deployment location of the unassociatedtelemetric device 201 and the telemetric device 201 can be configured tooperate in accordance with an automatic action rule. The processor ofthe unassociated telemetric device 201 can be configured to receiveunassociated telemetric device location information from the locationsensing device to provide to the processor the unassociated telemetricdevice location information in response to the device operating inaccordance with the automatic action rule which may trigger providingthe location information to the remote server. The unassociatedtelemetric device 201 can be configured to transmit the unassociatedtelemetric device location information and the remote server 217 can beconfigured to receive the unassociated telemetric device locationinformation. The remote server 217 can be configured to correlate theunassociated telemetric device location information with the deploymentor target location information and the remote server can be configuredto electronically change the unassociated telemetric device into anassociated telemetric device so that when the associated telemetricdevice generates quantity or usage information, the quantity or usageinformation transmitted by the associated telemetric device is appliedto a data store of the remote server related to the vessel identityinformation. It is understood that a remote server may be a collectionof devices and/or mobile device, in the cloud or/and in any suitableconfiguration. Once a match is made, it may be desirable to initiate averification process wherein an operator verifies the match manually.

A data store or a database can contain separate records for theunassociated telemetric device 201 and asset 202. The asset record caninclude a GLS for a target location the area inside a circular region204, or any other suitable dimensions. The unassociated telemetricdevice can transmit information about its location (based on GPSsignals) which indicate it has a GLS indicated by the dashed circle 205.

FIG. 14 shows the same device 201 and asset 202 after they have beeninstalled at the installation zone. The estimated GLS 205 of thetelemetric device is fully within the circumference of the GLS 204 ofthe target location, which triggers the system to automaticallyelectronically change the unassociated telemetric device into anassociated telemetric device. In so doing, the system can make anassociation in the database between the unassociated telemetric devicerecord and the asset record so that when the associated telemetricdevice generates quantity or usage information, the quantity or usageinformation transmitted by the associated telemetric device is appliedto a data store of the remote server related to the vessel identityinformation. This correlation or association may, for example, result ina link the fluid level in the gas vessel with gas delivery informationfor the vessel, which enables deliveries to that vessel to be scheduledefficiently and billed to the correct customer. Although billing isstrictly generated from the weights & measures meter on the truck, thetelemetric device makes it possible to check that the correct vessel wasbilled by comparing vessel level data from the telemetric device withthe amount and time of a fill from the truck meter.

EXAMPLE 2

FIG. 15 is a plan view of an asset 210 installed at a deploymentlocation without a telemetric device 211. A database contains separaterecords for the asset 210 and unassociated telemetric device 211. Theasset record includes a GLS for a target location which is the areainside a circular region 212. The unassociated telemetric device 211transmits information about its GLS (based on GPS signals) whichindicate its GLS is defined by a dashed circle 213, and is locatedoutside the target location 212.

FIG. 16 shows the same device 211 after being installed at the asset210. The GLS 213 of the unassociated device is now fully within thetarget location 212, which triggers an automatic electronic change ofthe unassociated device into an associated device so that there can bean association in the database between the device record and the assetrecord.

As described, the target location information can define a firstgeographical boundary and the telemetric device location information candefine a second geographical boundary or boundary dimension which canrepresent a geographical boundary, for example in size, and the step ofdetermining whether the unassociated telemetric device is located at thetarget location comprises determining whether the second geographicboundary overlaps the first geographical boundary according to apredefined rule. Therefore, the remote server 217 or other device suchas a mobile device can be configured to receive target locationinformation indicative of an asset deployment location, the targetlocation information providing a geographical boundary. The remoteserver can be configured to receive and/or store a boundary dimension orsecond geographical boundary for the telemetric device, wherein when thedevice location information is received, the boundary dimension isapplied to the device location information to determine if thegeographical boundary and the boundary dimension overlap, and thereforewhether the unassociated telemetric device is within a proximity to thedeployment location. In this way, overlap of these geographicaldimensions can indicate that the unassociated telemetric device hasreached the target location.

Rules

Below, the various automatic action rules are described including:

-   -   receiving the telemetric device location information, for        example, on a periodic basis, a random basis or a scheduled        basis;    -   receiving quantity or usage-event data by the telemetric device;        and/or receiving an indication of an activation event, to        generate event data.

The system can include rules, such as automatic action rules relating tothe operation of the system and can include automatic actions performedby system management software (e.g. software on a server) remote fromthe telemetric device. The rules can also include one or more triggersfor each action. Examples of actions and their triggers include:

-   -   starting a customer billing cycle, triggered the first time the        telemetric device is detected at a target location;    -   ending a customer billing cycle, triggered the first time the        telemetric device is detected to have left a target location;    -   sending an instruction from a remote server to the telemetric        device regarding its operation.

The rules can also specify the sending of particular instructions to atelemetric device and the circumstances in which they are sent. Examplesof instructions that can be sent to the telemetric device include:

-   -   measure particular kinds of data at particular times e.g. gas        level and faults every four hours;    -   start transmitting particular kinds of data e.g. device        identifier, location, faults, gas level measurements;    -   stop transmitting particular kinds of data;    -   transmit particular kinds of data at particular intervals of        time e.g. daily, weekly, monthly;    -   transmit particular kinds of data at particular times of the day        e.g. 02:00 hours.

The rules can also specify circumstances in which the telemetric devicetransmits information.

For example, the rules may specify that the telemetric device istriggered to transmit information in response to:

-   -   time elapsed: the device is triggered to transmit information at        predetermined time;    -   intervals e.g. every 30 minutes (However, each location check        consumes battery power. The battery life will be shortened if        the device is in transit or storage for an extended period);    -   connection to a sensor: the device is triggered to transmit        information when it receives data from a sensor, such as a fluid        level sensor;    -   change in fluid level may indicate a fill-event and therefore        the unassociated device may provide fill-event data: the device        is triggered to transmit information when it detects a        particular pattern of change in fluid level data. For example,        the first time the fluid level rises—which means the vessel is        being filled for the first time—can activate a device to start        transmitting location data and auto-associate the device with        the vessel. This fill-event may occur at the target location as        opposed to a fill event occurring, for example, occurring at the        depot where new tanks are stored. At the depot, a fill-event may        occur, for example, for the purpose of testing the asset or        vessel, to generate event data. It is understood that the rules        may be modified and/or new rules can be added and/or a rule may        be combined with another rule;    -   acceleration profile: the device is triggered to transmit        information when a particular pattern of acceleration is        detected in the device (for example by an accelerometer in the        device) for example, an acceleration profile produced by an        installer mechanically tapping the device in a particular        pattern which is consistent with an activation event, to        generate event data;    -   magnetic data: a particular pattern of magnetic field data can        trigger the device. For example, the trigger can be initiated        when the device is attached to a magnetic float gauge, or by an        installer passing a magnet over the device in a particular        pattern;    -   removal of a mechanical seal or keeper: removal of a mechanical        seal triggers the device;    -   manual triggering: for example, by activating a button or switch        on the telemetric device;    -   combinations of the above e.g. remove keeper then magnetic        activation.

There can be multiple target locations. Each target location can belinked with rules about the operation of the system, for example rulesabout the operation of the telemetric device and its interactions withother parts of the system. For example, the system can include rules fora target location which defines the information should be transmitted bythe telemetric device and when it should be transmitted.

For example, a rule can define that a telemetric device should nottransmit fluid level information until the telemetric device has beendelivered to the target location, which is the site of a gas vessel.This type of rule can save battery power and communication costs beingincurred before the telemetric device arrives at the gas vessel.

Example 1: When the telemetric device is detected to be at a targetlocation which is the deployment site of a vessel, a server transmits aninstruction to the telemetric device to make two types of transmission:

-   -   a daily transmission at 02:00 hours of device identifier,        faults, gas level measurements; and/or a weekly or monthly        transmission at 02:00 hours with the same information plus the        location of the telemetric device measured by GNSS (reducing the        number of times at which the device calculates geographical        location by GNSS helps to extend the battery life).

Example 2: When the telemetric device is detected to be at targetlocation which is a depot where vessels are held temporarily (e.g. forrefurbishment or awaiting deployment), a server transmits an instructionto the device to make only one type of transmission:

-   -   a daily transmission at 02:00 hours of the location of the        telemetric device measured by GNSS (gas levels are not monitored        while in the depot).

The system can include rules which define the circumstances for atelemetric device to be deemed to be located at the target location. Therules can take many forms, for example:

-   -   A telemetric device to be deemed to be located at the target        location when 100% of a GLS for the telemetric device overlaps        with a GLS for the target location.    -   A telemetric device to be deemed to be located at the target        location when at least 50% of a GLS for the telemetric device        overlaps with a GLS for the target location.    -   A telemetric device to be deemed to be located at the target        location when at least x % of a GLS for the telemetric device        overlaps with a GLS for the target location, where x is defined        in the rule and is greater than 0 and up to 100.    -   A telemetric device to be deemed to be located at the target        location when at least y % of a GLS for the target location        overlaps with a GLS for the telemetric device, where y is        defined in the rule and is greater than 0 and up to 100.        Validation Conditions:

As a cross check, validation can be performed to further refine theprocess to assure that the now associated telemetric device isappropriate and/or unique. Accordingly, it may be automatically assuredthat the associated telemetric device is reporting quantity or usagedate relating to the correct vessel or asset. To validate, an asset maybe identified by attributes, such as vessel or asset capacity ororientation, such as vertical or horizontal. If a device that isconfigured to operate with a vessel or asset having a different capacityor orientation than that expected at the target location, then avalidation may fail. Accordingly, various conditions or rules may be setup and/or applied to validate that that the associated telemetric deviceis reporting quantity or usage date relating to the correct vessel orasset. In the event that automatic validation conditions cannot beaffected, then manual validation conditions might be required. Ifneither the automatic nor the manual validation can occur, then themethod may include automatic disassociation, or otherwise, theunassociated telemetric device does not become an associated telemetricdevice.

Automatic Disassociation Conditions:

Disassociation may occur in the event that the associated electronicdevice is separated from the vessel or other type of asset, or theboundaries of their respective locations separate so that they do notoverlap to a sufficient degree or at all. In that case, a differentunassociated telemetric device might become an associated telemetricdevice. This may occur for example, when the device needs to bereplaced, or if the vessel or asset is moved.

Determining the Location of the Telemetric Device

Many location-sensing methods can be used to determine the location ofthe telemetric device, a location sensing device may be for example:

-   -   GNSS;    -   Wi-Fi positioning (which requires access to a database of Wi-Fi        networks and their locations);    -   network-supported location services (cell tower triangulation        for example GSM or LTE, satellite communications, low-power        wide-area network or LPWAN (public and private) for example LoRa        or Sigfox, or web browser Geolocation API);    -   dead reckoning: calculate location relative to a previous known        location e.g. gyroscope and accelerometer chip;    -   direction and range finding technologies;    -   the address of a fixed telephone line service.        Telemetry Examples

Many telemetry techniques may be used to enable the telemetric device totransmit and receive data, for example:

-   -   fixed telephone or internet line (copper, fibre);    -   cellular network;    -   LPWAN (public and private) e.g. LoRa, Sigfox;    -   private radio link e.g. ISM band;    -   Wi-Fi;    -   satellite communications.

Optionally, the telemetric device can be arranged to transmit to anothertelemetric device which is capable of transmitting to a network. Forexample, the transmission between telemetric devices can be throughprivate radio link, and the transmission to the network can be via acellular network, LPWAN or fixed telephone or internet line.

The Telemetric Device

There are at least two categories of telemetric device:

1. a telemetric device capable of determining its own location, such aswith GNSS or Wi-Fi sniffing (which requires access to an externaldatabase of Wi-Fi networks and their locations);

2. a telemetric device which can be located externally by triangulationfrom a network, such as a cell phone or LPWAN network.

In both cases, the telemetric device may include:

-   -   hardware for communicating with the data network (e.g. cell        communications, LPWAN, private radio link, satellite, Wi-Fi);    -   a microcontroller to process information and coordinate        components in the telemetric device.

Where the telemetric device is capable of determining its own location,it further includes hardware, such as a GNSS receiver.

The telemetric device can also have one or more sensors, such as a gaslevel sensor, but this is not essential in all embodiments.

FIG. 17 shows an example of the information contained in an SQL databasetable 230 for a telemetric device and an SQL database table 232 for anasset. The table 230 for the telemetric device is called device_recordand contains information related to a telemetric device. The table 232is called asset_record and contains information related to an asset. Inthe device_record table 230, the device_id column is a primary key, andin the asset record table 232, the asset_id column is a primary key.Neither the device_record table 230 nor the asset_record table 232contain data in both the device_id and device_record columns. The tables230, 232 in FIG. 17 are therefore not associated and cannot be joined.While this embodiment uses an SQL database, generally any suitablerelational or non-relational database or data store may be used.

The device_record table 230 contains location information (a GLS) forthe telemetric device in fields called Lat, Long and precision. Theasset_record table 232 contains a GLS for a target location in fieldscalled Lat, Long and radius. The device is not located at the targetlocation, as indicated by the different Lat and Long data in the twotables 230, 232.

FIG. 18 shows an updated version of the tables in FIG. 17 after newlocation data has been received from the unassociated telemetric deviceand added to the device_record table 234 in the Lat and Long columns.The Lat and Long data in the device_record table 234 now match the Latand Long data in the asset_record table 236, which means the telemetricdevice is located at the target location. The system has compared theLat and Long data in the two tables 234, 236 and identified that thereis a match. The match has triggered the system to automaticallyassociate the device_record table 234 with the asset_record table 236 bycopying the asset_id information in the asset_record table 236 into theasset_id field of the device_record table 234. A join command can now beused to join these two records using the asset_id column.

In the example shown in FIGS. 17 and 18, the quantity informationtransmitted by the telemetric device is not included in thedevice_record table 230, 234. The quantity information is stored in aseparate table (not shown) associated with the device_record table byhaving the same device_id column populated with data.

Associating sets of information X and Y is understood here to meanrelating X and Y, either directly or indirectly, so that if X is knownthen Y can be ascertained (and vice versa). In a relational database,tables X and Y are associated if they can be joined.

System Architecture

Different embodiments of a system for monitoring a quantity related toan asset may have different architectures.

FIG. 19 shows an example of an architecture in an embodiment of asystem. The telemetric device 301 is installed at an asset 302 such as agas vessel. The telemetric device is equipped for wireless communicationvia a data network 303 to a server 304 which runs software processes tocoordinate the system. The server is linked to a database 305 to storeinformation for example information related to the telemetric device 301and information related to the asset 302. The wireless communication canbe implemented in many ways, such as a cellular network,

LPWAN, or even satellite communications.

FIG. 20 show another example of a system architecture, where partssimilar or identical to those in FIG. 13 are similarly indicated. Inthis example, the telemetric device 301 communicates via a fixed line toa modem 306 which communicates via PSTN with the data network 303.

FIG. 21 shows another example of a system architecture. In this example,the telemetric device 301 communicates via a private radio link with atransmitter 307 which communicates via PSTN with the data network 303.

Now that embodiments have been described, it will be appreciated thatsome embodiments may have some of the following advantages:

-   -   Data entry errors may be reduced or eliminated.    -   Manual communication of identifiers may be reduced or        eliminated, reducing labour and costs.    -   Lower skilled workers may be required because processes are        automated.    -   Customer billing may be initiated at the time of association of        identifiers.    -   Location sensing may reduce the number of lost things.

Variations and/or modifications may be made to the embodiments describedwithout departing from the spirit or ambit of the invention. The presentembodiments are, therefore, to be considered in all respects asillustrative and not restrictive. Reference to a feature disclosedherein does not mean that all embodiments must include the feature.

Prior art, if any, described herein is not to be taken as an admissionthat the prior art forms part of the common general knowledge in anyjurisdiction.

In the claims which follow and in the preceding description of theinvention, except where the context requires otherwise due to expresslanguage or necessary implication, the word “comprise” or variationssuch as “comprises” or “comprising” is used in an inclusive sense, thatis to specify the presence of the stated features but not to precludethe presence or addition of further features in various embodiments ofthe invention.

The invention claimed is:
 1. A method of a system for automaticallyelectronically disassociating an associated telemetric device whereinthe associated telemetric device is associated with a vessel identity ata remote server, the system including rules relating to the operation ofthe system, the associated telemetric device comprising a processor andbeing configured to detect and transmit quantity or usage data and beingconfigured for location sensing, wherein the associated telemetricdevice is configured to communicate with a remote server, the methodcomprising: the associated telemetric device operating in accordancewith a rule comprising an automatic action rule; in response to theassociated telemetric device operating in accordance with the automaticaction rule, the processor receiving location information of theassociated telemetric device; the associated telemetric devicetransmitting the location information; the remote server receiving thelocation information; the remote server determining whether theassociated telemetric device is separated from the vessel or whetherboundaries of the locations of the associated telemetric device and thetarget location are separated so that they do not overlap to asufficient degree or at all; if the remote server determines that theassociated telemetric device is separated from the vessel or whetherboundaries of the locations of the associated telemetric device and thetarget location are separated so that they do not overlap to asufficient degree or at all, disassociating the associated telemetricdevice so that the associated telemetric device becomes a disassociatedtelemetric device.
 2. The method of claim 1 wherein the associatedtelemetric device further comprises an accelerometer, wherein theautomatic action rule is triggered when the associated telemetric deviceis detected to have moved according to the accelerometer.
 3. The methodof claim 1 wherein the automatic action rule triggers the associatedtelemetric device to detect that it has moved according to the locationsensing; the associated telemetric device transmitting the locationinformation to the remote server.
 4. A system for automaticallyelectronically disassociating an associated telemetric device whereinthe associated telemetric device is associated with a vessel identity ata remote server, the system including rules relating to the operation ofthe system, the associated telemetric device comprising a processor andbeing configured to detect and transmit quantity or usage data and beingconfigured for location sensing, wherein the associated telemetricdevice is configured to communicate with a remote server, the systemcomprising: the associated telemetric device configured to operate inaccordance with a rule comprising an automatic action rule; in responseto the associated telemetric device operating in accordance with theautomatic action rule, the processor configured to receive locationinformation of the associated telemetric device from the locationsensing; the associated telemetric device configured to transmit thelocation information; the remote server configured to receive thelocation information; the remote server configured to determine whetherthe associated telemetric device is separated from the vessel or whetherboundaries of the locations of the associated telemetric device and thetarget location are separated so that they do not overlap to asufficient degree or at all; if the remote server determines that theassociated telemetric device is separated from the vessel or whetherboundaries of the locations of the associated telemetric device and thetarget location are separated so that they do not overlap to asufficient degree or at all, the remote server configured todisassociate the associated telemetric device so that the associatedtelemetric device becomes a disassociated telemetric device.
 5. Thesystem of claim 4 wherein the associated telemetric device furthercomprises an accelerometer, wherein the automatic action rule istriggered when the associated telemetric device is detected to havemoved according to the accelerometer.
 6. The system of claim 4 whereinthe automatic action rule is configured to trigger the associatedtelemetric device to detect that it has moved according to the locationsensing; the associated telemetric device is configured to transmit thelocation information to the remote server.
 7. A system for automaticallyelectronically associating asset identity information of an asset withan unassociated telemetric device, the unassociated telemetric devicecomprising a processor and being configured to detect and transmitquantity or usage data and being configured for location sensing,wherein the unassociated telemetric device is configured to communicatewith a remote server, the method comprising the steps of: the remoteserver configured to receive the asset identity information comprising adeployment location for the unassociated telemetric device; theunassociated telemetric device configured to operate in accordance withan automatic action rule; in response to the unassociated telemetricdevice operating in accordance with the automatic action rule, theprocessor being configured to receive location information of theunassociated telemetric device according to the location sensing; theunassociated telemetric device configured for location sensing; theremote server configured to receive the location information; the remoteserver configured to correlate the location information with the assetidentity information when resolving that the location informationrepresents that the unassociated telemetric device is within a proximityto the deployment location, and the remote server being configured toautomatically electronically associate the unassociated telemetricdevice with the asset identity information, resulting in theunassociated telemetric device becoming an associated telemetric device,so that when the associated telemetric device generates quantity orusage information, the quantity or usage information transmitted by theassociated telemetric device is applied to a data store of the remoteserver related to the asset identity information.
 8. The system of claim7, wherein operating in accordance with the automatic action rulecomprises at least one of receiving the location information of theunassociated telemetric device, receiving quantity or usage event datatransmitted by the unassociated telemetric device and receiving anindication of an activation event of the unassociated telemetric device.9. The system of claim 7 wherein the deployment location defines a firstgeographical boundary and the location information defines a secondgeographical boundary, and correlating the location information with theasset identity information comprises determining whether the secondgeographic boundary overlaps with the first geographical boundaryaccording to a predefined rule.
 10. The system of claim 7 furthercomprising the remote server being configured to automatically validatethe correlation of the associated telemetric device with the deploymentlocation in accordance with validation conditions.
 11. The system ofclaim 7 further comprising the remote server being configured todisassociate the associated telemetric device from the asset identityinformation.